SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Batch processing</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Batch processing</span></span>

</h1>

</header>

<p>In computing, <b>batch processing</b> is the running of a <a href="Software" title="Software">software</a> <a href="Job_(computing)" title="Job (computing)">job</a> in an <a href="Computer_Automation" title="Computer Automation"> automated</a> and unattended way. A <a href="Computer_user" class="mw-redirect" title="Computer user"> user</a> schedules a job to run and then waits for a processing system to run it. Typically, a job is scheduled to run at a configured <a href="Time_of_day" class="mw-redirect" title="Time of day">time of day</a> or when an <a href="Event_(computing)" title="Event (computing)">event</a> occurs or when <a href="Computer_resource" class="mw-redirect" title="Computer resource">computer resources</a> are available.

</p>

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

<p>The term "batch processing" originates in the traditional classification of <a href="Methods_of_production" title="Methods of production">methods of production</a> as <a href="Job_production" title="Job production">job production</a> (one-off production), <a href="Batch_production" title="Batch production">batch production</a> (production of a "batch" of multiple items at once, one stage at a time), and <a href="Flow_production" class="mw-redirect" title="Flow production">flow production</a> (mass production, all stages in process at once).

</p>

<div class="mw-heading mw-heading3"><h3 id="Early_history">Early history</h3></div>

<p>Early computers were capable of running only one program at a time. Each user had sole control of the machine for a scheduled period of time. They would arrive at the computer with program and data, often on <a href="Punch_card" class="mw-redirect" title="Punch card">punched paper cards</a> and magnetic or paper tape, and would load their program, run and debug it, and carry off their output when done.

</p><p>As computers became faster the setup and takedown time became a larger percentage of available computer time. Programs called <i>monitors</i>, the forerunners of <a href="Operating_system" title="Operating system">operating systems</a>, were developed which could process a series, or "batch", of programs, often from <a href="Magnetic-tape_data_storage" title="Magnetic-tape data storage">magnetic tape</a> prepared offline. The monitor would be loaded into the computer and run the first job of the batch. At the end of the job it would regain control and load and run the next until the batch was complete. Often the output of the batch would be written to magnetic tape and printed or punched offline. Examples of monitors were IBM's <i>Fortran Monitor System</i>, SOS (Share Operating System), and finally <a href="IBM_7090/94_IBSYS" title="IBM 7090/94 IBSYS">IBSYS</a> for IBM's <a href="IBM_700/7000_series" title="IBM 700/7000 series">709x</a> systems in 1960.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Third-generation_systems">Third-generation systems</h3></div>

<p><span class="cleanup-needed-content" style="padding-left:0.1em; padding-right:0.1em; color:var(--color-subtle, #54595d); border:1px solid var(--border-color-subtle, #c8ccd1);"><a href="Third-generation_computer" class="mw-redirect" title="Third-generation computer">Third-generation computers</a></span><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> capable of <a href="Multiprogramming" class="mw-redirect" title="Multiprogramming">multiprogramming</a> began to appear in the 1960s. Instead of running one batch job at a time, these systems can have multiple batch programs running at the same time in order to keep the system as busy as possible. One or more programs might be awaiting input, one actively running on the CPU, and others generating output. Instead of offline input and output, programs called <a href="Spooler" class="mw-redirect" title="Spooler">spoolers</a> read jobs from cards, disk, or remote terminals and place them in a <a href="Batch_queue" class="mw-redirect" title="Batch queue">job queue</a> to be run. In order to prevent <a href="Deadlock_(computer_science)" title="Deadlock (computer science)">deadlocks</a> the <a href="Job_scheduler" title="Job scheduler">job scheduler</a> needs to know each job's resource requirements—memory, magnetic tapes, mountable <a href="Disk_storage" title="Disk storage">disks</a>, etc., so various scripting languages were developed to supply this information in a structured way. Probably the most well-known is IBM's <i><a href="Job_Control_Language" title="Job Control Language">Job Control Language</a></i> (JCL). Job schedulers select jobs to run according to a variety of criteria, including priority, memory size, etc. <a href="Remote_job_entry" title="Remote job entry">Remote batch</a> is a procedure for submitting batch jobs from remote terminals, often equipped with a <a href="Punch_card_reader" class="mw-redirect" title="Punch card reader">punch card reader</a> and a <a href="Line_printer" title="Line printer">line printer</a>.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup> Sometimes <a href="Asymmetric_multiprocessing" title="Asymmetric multiprocessing">asymmetric multiprocessing</a> is used to spool batch input and output for one or more large computers using an attached smaller and less-expensive system, as in the IBM System/360 <a href="Attached_Support_Processor" title="Attached Support Processor">Attached Support Processor</a>.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>a<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Later_history">Later history</h3></div>

<p>The first general purpose time sharing system, <a href="Compatible_Time-Sharing_System" title="Compatible Time-Sharing System">Compatible Time-Sharing System</a> (CTSS), was compatible with batch processing. This facilitated transitioning from batch processing to <a href="Interactive_computing" title="Interactive computing">interactive computing</a>.<sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p><p>From the late 1960s onwards, interactive computing such as via text-based <a href="Computer_terminal" title="Computer terminal">computer terminal</a> interfaces (as in <a href="Unix_shell" title="Unix shell">Unix shells</a> or <a href="Read-eval-print_loop" class="mw-redirect" title="Read-eval-print loop">read-eval-print loops</a>), and later <a href="Graphical_user_interface" title="Graphical user interface">graphical user interfaces</a> became common. Non-interactive computation, both one-off jobs such as compilation, and processing of multiple items in batches, became retrospectively referred to as <i>batch processing</i>, and the term <i>batch job</i> (in early use often "batch <i>of</i> jobs") became common. Early use is particularly found at the <a href="University_of_Michigan" title="University of Michigan">University of Michigan</a>, around the <a href="Michigan_Terminal_System" title="Michigan Terminal System">Michigan Terminal System</a> (MTS).

</p><p>Although timesharing did exist, its use was not robust enough for corporate data processing; none of this was related to the earlier <a href="Unit_record_equipment" title="Unit record equipment">unit record equipment</a>, which was human-operated.

</p>

<div class="mw-heading mw-heading3"><h3 id="Ongoing">Ongoing</h3></div>

<p>Non-interactive computation remains pervasive in computing, both for general data processing and for system "housekeeping" tasks (using <a href="System_software" title="System software">system software</a>). A high-level program (executing multiple programs, with some additional "glue" logic) is today most often called a <i>script</i>, and written in <a href="Scripting_language" title="Scripting language">scripting languages</a>, particularly <a href="Shell_script" title="Shell script">shell scripts</a> for system tasks; in <a href="IBM_PC_DOS" title="IBM PC DOS">IBM PC DOS</a> and <a href="MS-DOS" title="MS-DOS">MS-DOS</a> this is instead known as a <a href="Batch_file" title="Batch file">batch file</a>. That includes <a href="Unix" title="Unix">UNIX</a>-based computers, <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a>, <a href="MacOS" title="MacOS">macOS</a> (whose foundation is the <a href="Berkeley_Software_Distribution" title="Berkeley Software Distribution">BSD</a> Unix kernel), and even <a href="Smartphone" title="Smartphone">smartphones</a>. A running script, particularly one executed from an interactive <a href="Login_session" title="Login session">login session</a>, is often known as a <a href="Job_(Unix)" class="mw-redirect" title="Job (Unix)">job</a>, but that term is used very ambiguously.

</p><p>"There is no direct counterpart to z/OS batch processing in PC or UNIX systems. Batch jobs are typically executed at a scheduled time or on an as-needed basis. Perhaps the closest comparison is with processes run by an <a href="At_(command)" title="At (command)">at</a> or <a href="Cron" title="Cron">cron</a> command in UNIX, although the differences are significant."<sup id="cite_ref-whatis_8-0" class="reference"><a href="#cite_note-whatis-8"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Modern_systems">Modern systems</h2></div>

<p>Batch applications are still critical in most organizations in large part because many common business processes are amenable to batch processing. While online systems can also function when manual intervention is not desired, they are not typically optimized to perform high-volume, repetitive tasks. Therefore, even new systems usually contain one or more batch applications for updating information at the end of the day, generating reports, printing documents, and other non-interactive tasks that must complete reliably within certain business deadlines.

</p><p>Some applications are amenable to flow processing, namely those that only need data from a single input at once (not totals, for instance): start the next step for each input as it completes the previous step. In this case flow processing lowers <a href="Latency_(engineering)" title="Latency (engineering)">latency</a> for individual inputs, allowing them to be completed without waiting for the entire batch to finish. However, many applications require data from all records, notably computations such as totals. In this case the entire batch must be completed before one has a usable result: partial results are not usable.

</p><p>Modern batch applications make use of modern batch frameworks such as Jem The Bee, <a href="Spring_Batch" title="Spring Batch">Spring Batch</a><sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> or implementations of <a href="Java_Specification_Request" class="mw-redirect" title="Java Specification Request">JSR</a> 352<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> written for <a href="Java_(programming_language)" title="Java (programming language)">Java</a>, and other frameworks for other programming languages, to provide the <a href="Fault_tolerance" title="Fault tolerance">fault tolerance</a> and <a href="Scalability" title="Scalability">scalability</a> required for high-volume processing. In order to ensure high-speed processing, batch applications are often integrated with <a href="Grid_computing" title="Grid computing">grid computing</a> solutions to <a href="Partition_of_a_set" title="Partition of a set">partition</a> a batch job over a large number of processors, although there are significant programming challenges in doing so. High volume batch processing places particularly heavy demands on system and application architectures as well. Architectures that feature strong <a href="Input/output" title="Input/output">input/output</a> performance and vertical <a href="Scalability" title="Scalability">scalability</a>, including modern <a href="Mainframe_computers" class="mw-redirect" title="Mainframe computers">mainframe computers</a>, tend to provide better batch performance than alternatives.

</p><p><a href="Scripting_languages" class="mw-redirect" title="Scripting languages">Scripting languages</a> became popular as they evolved along with batch processing.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Batch_window">Batch window</h2></div>

<p>A <i>batch window</i> is "a period of less-intensive online activity",<sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> when the computer system is able to run batch jobs without interference from, or with, interactive online systems.

</p><p>A bank's <i>end-of-day (EOD)</i> jobs require the concept of <i>cutover</i>, where transaction and data are cut off for a particular day's batch activity ("deposits after 3 PM will be processed the next day").

</p><p>As requirements for online systems uptime expanded to support <a href="Globalization" title="Globalization">globalization</a>, the <a href="Internet" title="Internet">Internet</a>, and other business needs, the batch window shrank<sup id="cite_ref-Rbook_13-0" class="reference"><a href="#cite_note-Rbook-13"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-14" class="reference"><a href="#cite_note-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> and increasing emphasis was placed on techniques that would require online data to be available for a maximum amount of time.

</p>

<div class="mw-heading mw-heading2"><h2 id="Batch_size">Batch size</h2></div>

<p>The <i>batch size</i> refers to the number of work units to be processed within one batch operation. Some examples are:

</p>

<ul><li>The number of lines from a file to load into a database before <a href="Commit_(data_management)" title="Commit (data management)">committing</a> the transaction.</li>

<li>The number of messages to dequeue from a queue.</li>

<li>The number of requests to send within one payload.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Common_batch_processing_usage">Common batch processing usage</h2></div>

<ul><li>Efficient bulk database updates and automated <a href="Transaction_processing" title="Transaction processing">transaction processing</a>, as contrasted to interactive <a href="Online_transaction_processing" title="Online transaction processing">online transaction processing</a> (OLTP) applications. The <a href="Extract%2C_transform%2C_load" title="Extract, transform, load">extract, transform, load</a> (ETL) step in populating <a href="Data_warehouses" class="mw-redirect" title="Data warehouses">data warehouses</a> is inherently a batch process in most implementations.</li>

<li>Performing bulk operations on <a href="Digital_image" title="Digital image">digital images</a> such as resizing, conversion, watermarking, or otherwise editing a group of image files.</li>

<li>Converting computer files from one format to another. For example, a batch job may convert proprietary and legacy files to common standard formats for end-user queries and display.</li>

<li>Training <a href="Machine_learning" title="Machine learning">Machine Learning</a> models. For example, an <a href="E-commerce" title="E-commerce">e-commerce</a> website might want to process customer transactions in an hourly batch to update the model that produces related <a href="Product_recommendations" class="mw-redirect" title="Product recommendations">product recommendations</a>, in order to save <a href="Computational_resource" title="Computational resource">computational resources</a>.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notable_batch_scheduling_and_execution_environments">Notable batch scheduling and execution environments</h2></div>

<p>The <a href="IBM_mainframe" title="IBM mainframe">IBM mainframe</a> <a href="Z/OS" title="Z/OS">z/OS</a> <a href="Operating_system" title="Operating system">operating system</a> or platform has arguably the most highly refined and evolved set of batch processing facilities owing to its origins, long history, and continuing evolution. Today such systems commonly support hundreds or even thousands of concurrent online and batch tasks within a single <a href="Operating_system" title="Operating system">operating system</a> image. Technologies that aid concurrent batch and online processing include <a href="Job_Control_Language" title="Job Control Language">Job Control Language</a> (JCL), scripting languages such as <a href="REXX" class="mw-redirect" title="REXX">REXX</a>, Job Entry Subsystem (<a href="JES2" class="mw-redirect" title="JES2">JES2</a> and <a href="JES3" class="mw-redirect" title="JES3">JES3</a>), <a href="Workload_Manager" title="Workload Manager">Workload Manager</a> (WLM), Automatic Restart Manager (ARM), Resource Recovery Services (RRS), <a href="IBM_Db2" title="IBM Db2">IBM Db2</a> data sharing, <a href="Parallel_Sysplex" class="mw-redirect" title="Parallel Sysplex">Parallel Sysplex</a>, unique performance optimizations such as <a href="HiperDispatch" title="HiperDispatch">HiperDispatch</a>, <a href="Channel_I/O" title="Channel I/O">I/O channel architecture</a>, and several others.

</p><p>The Unix programs <code><a href="Cron_(Unix)" class="mw-redirect" title="Cron (Unix)">cron</a></code>, <code><a href="At_(command)" title="At (command)">at</a></code>, and <code><a href="Batch_(Unix)" class="mw-redirect" title="Batch (Unix)">batch</a></code> (today <code>batch</code> is a variant of <code>at</code>) allow for complex scheduling of jobs. Windows has a <a href="Job_scheduler" title="Job scheduler">job scheduler</a>. Most <a href="High-performance_computing" title="High-performance computing">high-performance computing</a> <a href="Cluster_(computing)" class="mw-redirect" title="Cluster (computing)">clusters</a> use batch processing to maximize cluster usage.<sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup>

</p>

<ul><li><a href="Background_process" title="Background process">Background process</a></li>

<li><a href="Batch_file" title="Batch file">Batch file</a></li>

<li><a href="Batch_renaming" title="Batch renaming">Batch renaming</a> – to rename lots of files automatically without human intervention, in order to save time and effort</li>

<li><a href="BatchPipes" title="BatchPipes">BatchPipes</a> – for utility that increases batch performance</li>

<li><a href="Processing_modes" class="mw-redirect" title="Processing modes">Processing modes</a></li>

<li><a href="Production_support" title="Production support">Production support</a> – for batch job/schedule/stream support</li>

<li><a href="High-throughput_computing" title="High-throughput computing">High-throughput computing</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-lower-alpha">

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text">Use of satellite computers for this purpose began earlier, e.g., in IBM <a href="IBM_7090#7094/7044_Direct_Coupled_System" title="IBM 7090">7094/7044 Direct Coupled System</a>.</span>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.softwarepreservation.org/projects/os/dc.html">"The Direct Couple for the IBM 7090"</a>. <i>SoftwarePreservationGroup.org</i>. <q>IBSYS was an operating system for the 7090 that evolved from SOS (SHARE Operating System)</q></cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://ghostarchive.org/archive/20221009/https://courses.cs.washington.edu/courses/cse451/16wi/readings/lecture_readings/LCM_OperatingSystemsTimeline_Color_acd_newsize.pdf">"History of Operating Systems"</a> <span class="cs1-format">(PDF)</span>. Archived from <a rel="nofollow" class="external text" href="https://courses.cs.washington.edu/courses/cse451/16wi/readings/lecture_readings/LCM_OperatingSystemsTimeline_Color_acd_newsize.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2022-10-09.</cite></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite class="citation news cs1"><a rel="nofollow" class="external text" href="https://www.theregister.co.uk/2014/04/07/ibm_s_360_50_anniversary">"Why won't you DIE? IBM's S/360 and its legacy at 50"</a>. <i><a href="The_Register" title="The Register">The Register</a></i>. April 7, 2014.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://bitsavers.org/pdf/cdc/terminal/82128000_200_User_Terminal_Hardware_Reference_Jul68.pdf">"CDC User Terminal Hardware Reference manual"</a> <span class="cs1-format">(PDF)</span>. <i>BitSavers</i>. <a rel="nofollow" class="external text" href="https://ghostarchive.org/archive/20221009/http://bitsavers.org/pdf/cdc/terminal/82128000_200_User_Terminal_Hardware_Reference_Jul68.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 2022-10-09.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite id="CITEREFWaldenVan_Vleck2011" class="citation web cs1">Walden, David; <a href="Tom_Van_Vleck" title="Tom Van Vleck">Van Vleck, Tom</a>, eds. (2011). <a rel="nofollow" class="external text" href="https://multicians.org/thvv/compatible-time-sharing-system.pdf">"Compatible Time-Sharing System (1961-1973): Fiftieth Anniversary Commemorative Overview"</a> <span class="cs1-format">(PDF)</span>. IEEE Computer Society. <a rel="nofollow" class="external text" href="https://ghostarchive.org/archive/20221009/https://multicians.org/thvv/compatible-time-sharing-system.pdf">Archived</a> <span class="cs1-format">(PDF)</span> from the original on 2022-10-09<span class="reference-accessdate">. Retrieved <span class="nowrap">February 20,</span> 2022</span>. <q>CTSS was called "compatible" in the sense that <a href="History_of_IBM_mainframe_operating_systems#FORTRAN_Monitor_System" title="History of IBM mainframe operating systems">FMS</a> could be run in B-core as a "back-ground" user, nearly as efficiently as on a bare machine, and also because programs compiled for FMS batch could be loaded and executed in the "foreground" time-sharing environment (with some limitations). ... This feature allowed the Computation Center to make the transition from batch to timesharing gradually</q></cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite class="citation journal cs1">"The Computing Center: Coming to Terms with the IBM System/360 Model 67". <i>Research News</i>. <b>20</b> (Nov/Dec). University of Michigan: <a rel="nofollow" class="external text" href="https://books.google.com/books?id=Qs9VAAAAMAAJ&pg=RA1-PA122&dq=%22batch+job%22">10</a>. 1969.</cite></span>

</li>

<li id="cite_note-whatis-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-whatis_8-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFIBM_Corporation" class="citation web cs1">IBM Corporation. <a rel="nofollow" class="external text" href="https://www.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zconcepts/zconc_whatisbatch.htm">"What is batch processing?"</a>. <i>zOS Concepts</i><span class="reference-accessdate">. Retrieved <span class="nowrap">Oct 10,</span> 2019</span>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFMinella2011" class="citation book cs1">Minella, Michael (2011-10-13). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=2tOSxcKmdyoC&dq=history+of+batch+processing&pg=PA2"><i>Pro Spring Batch</i></a>. Apress. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4302-3453-1</bdi>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.jcp.org/en/jsr/detail?id=352">"Batch Applications for the Java Platform"</a>. Java Community Process<span class="reference-accessdate">. Retrieved <span class="nowrap">2015-08-03</span></span>.</cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20181020011704/https://www-01.ibm.com/support/docview.wss?uid=tss1wp102544&aid=5">"JSR352 null"</a>. IBM.com. Archived from <a rel="nofollow" class="external text" href="https://www-01.ibm.com/support/docview.wss?uid=tss1wp102544&aid=5">the original</a> on 2018-10-20<span class="reference-accessdate">. Retrieved <span class="nowrap">2018-10-19</span></span>. <q>JSR 352, the open standard specification for Java batch processing. ... The programming languages used evolved over time based on what was available</q></cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://publib.boulder.ibm.com/infocenter/zos/basics/index.jsp?topic=/com.ibm.zos.zmainframe/zconc_batchproc.htm">"Mainframes working after hours: Batch processing"</a>. <i>Mainframe concepts</i>. IBM Corporation<span class="reference-accessdate">. Retrieved <span class="nowrap">June 20,</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-Rbook-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-Rbook_13-0">^</a></b></span> <span class="reference-text"><cite class="citation book cs1"><a rel="nofollow" class="external text" href="https://www.oreilly.com/library/view/design-build/9780470257630/9780470257630_batch.html"><i>Batch Processing: Design – Build – Run: Applied Practices and Principles</i></a>. Oreilly. 2009-02-24. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9780470257630</bdi>.</cite></span>

</li>

<li id="cite_note-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-14">^</a></b></span> <span class="reference-text">"Traditionally batch was an overnight activity, with jobs processing millions of ... Today the batch window is ever decreasing with 24/7 availability requirements."</span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite id="CITEREFGutkovich2023" class="citation web cs1">Gutkovich, Ben (10 February 2023). <a rel="nofollow" class="external text" href="https://superlinked.com/insights/why-real-time-machine-learning-will-be-the-buzzword-of-2023">"Why Real-Time Machine Learning will be the Buzzword of 2023"</a>. <i>Superlinked</i><span class="reference-accessdate">. Retrieved <span class="nowrap">11 April</span> 2023</span>.</cite></span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.slideshare.net/raamana/high-performance-computing-with-checklist-and-tips-optimal-cluster-usage">"High performance computing tutorial, with checklist and tips to optimize"</a>. January 25, 2018. <q>a multi-user, shared and smart batch processing system improves the scale ..... Most <i>HPC</i> clusters are in Linux</q></cite></span>

</li>

</ol></div></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-08-02" href="https://en.wikipedia.org/wiki/?title=Batch_processing&oldid=1303865213">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>